Summary

This PR modifies the declare_rule! macro to automatically assign the correct RuleCategory to the metadata of a rule, instead of having to explicitly specify it as an associated constant on the Rule trait. This change relies on the specific module structure of the language analyzer implementations, specifically that rules are implemented in nested modules following the <category>::<group>::<rule> pattern in order to access information about the group of the rule using super, and information about the category using super::super.

I also decided to try and go one step further with this change by actually tying the rule to their group, and the groups to their category at the type system level (using an associated type on a trait). This means the category / group / rule hierarchy is now cyclic as each of these item knows both about it's parent and / or children, but that doesn't pose any problem in practice since this is only type-level metadata that gets resolved lazily by the Rust compiler as the generic code gets monomorphized. It does allow making a number of generic functions simple however, since they now only need to be generic on the type of a lint rule and can access the type of the group using the Group associated type, instead of being provided with the group as a second generic type.

Test Plan

This is mostly type-level only change, it should only have minimal impact on the how the code works. One notable exception is a change to the filtering code (filtering of categories and groups now happens earlier in the registry building code), but this behavior is largely covered by the existing analyzer tests.